Systems and method for lighting aisles

ABSTRACT

A lighting fixture for aisle lighting in a building includes processing electronics. The processing electronics are configured to cause the lighting fixture to provide increasing levels of illumination in response to state changes associated with sensed motion in the building.

BACKGROUND

Warehouses, retail stores, manufacturing plants, or other types ofbuildings (or outdoor spaces) are often organized to include aisles. Itis challenging and difficult to light aisles for energy efficiency andso that workers using the aisles have proper lighting (e.g., enough forthe task to be completed by the workers).

SUMMARY

One embodiment of the invention relates to a lighting fixture for energyefficient aisle lighting in a building. The lighting fixture includesprocessing electronics configured to cause the lighting fixture toprovide increasing levels of illumination in response to state changesassociated with sensed motion in the building. The state changes include(a) a transition from a no motion state to a local motion state (i.e.,transient motion); and (b) a transition from the local motion state(i.e., transient motion) to a sustained motion state.

Another embodiment of the invention relates to a system for energyefficient lighting of an aisle in a building. The system includes aplurality of lighting fixtures, wherein each of the plurality oflighting fixtures includes a motion sensor, transceiver, and processingelectronics. The processing electronics for each lighting fixture areconfigured to cause the respective lighting fixture to provideincreasing levels of illumination in response to state change associatedwith motion sensed by the motion sensor. The state changes include (a) atransition from a no motion state to a local motion state and (b) atransition from the local motion state to a sustained motion state.

Another embodiment of the invention relates to a method for providingenergy efficient lighting of an aisle in a building. The method includesusing a motion sensor and processing electronics coupled to a firstlighting fixture to distinguish between transient motion and sustainedmotion. The method further includes at the first lighting fixture,transitioning from a transient motion state to a sustained motion statein response to a determination of sustained motion. The method furtherincludes at the first lighting fixture, transitioning from a no motionstate to a local motion state in response to a determination of localmotion.

Alternative exemplary embodiments relate to other features andcombinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE FIGURES

The disclosure will become more fully understood from the followingdetailed description, taken in conjunction with the accompanyingfigures, wherein like reference numerals refer to like elements, inwhich:

FIGS. 1A-C illustrate three different states of a lighting fixture,according to an exemplary embodiment;

FIG. 2A is a perspective overhead view of a lighting fixture, accordingto an exemplary embodiment;

FIG. 2B is a block diagram of a facility lighting system for use withthe lighting fixtures of FIGS. 1A-C and FIG. 2, according to anexemplary embodiment;

FIG. 3 is a detailed block diagram of the controller of the facilitylighting system of FIG. 2B, according to an exemplary embodiment;

FIG. 4 is a detailed block diagram of the control computer of thefacility lighting system of FIG. 2B, according to an exemplaryembodiment;

FIG. 5 illustrates an exemplary control activity for a system ofcontrollers for a facility lighting system, according to an exemplaryembodiment;

FIG. 6 is a flow chart of a process for controlling multiple lightingfixtures in a zone based on sensor input, according to an exemplaryembodiment;

FIG. 7 illustrates how different lighting zones may be organized withina building having a facility lighting system, according to an exemplaryembodiment;

FIG. 8 is a flow chart of a process for providing an aisle lighting modeof operation using a lighting fixture controller and a system ofsimilarly configured lighting fixtures in a zone, according to anexemplary embodiment;

FIG. 9 is a flow chart of a process for providing an energy saving‘general’ mode of operation using a lighting fixture controller and asystem of similarly configured lighting fixtures in a zone, according toan exemplary embodiment;

FIG. 10 is a flow chart of a process for providing an energy saving‘task’ mode of operation using a lighting fixture controller and asystem of similarly configured lighting fixtures in a zone, according toan exemplary embodiment;

FIG. 11 is a flow chart of a process for providing a ‘step dimming’ modeof operation using a lighting fixture controller and a system ofsimilarly configured lighting fixtures in a zone, according to anexemplary embodiment;

FIG. 12 is a flow chart of a process for tracking and controllinglighting fixture duty cycle where the lighting fixture is configured totransition (e.g., turn on and off, change brightness levels) during theday according to motion-based control, according to an exemplaryembodiment; and

FIG. 13 is a flow chart of a process for tracking and controllinglighting fixture re-strike violation rules where the lighting fixture isconfigured to transition (e.g., turn on and off, change brightnesslevels) during the day according to motion-based control, according toan exemplary embodiment.

DETAILED DESCRIPTION

Before turning to the figures, which illustrate the exemplaryembodiments in detail, it should be understood that the application isnot limited to the details or methodology set forth in the descriptionor illustrated in the figures. It should also be understood that theterminology is for the purpose of description only and should not beregarded as limiting.

Referring generally to the Figures, a system of lighting fixtures isconfigured to control an aisle, set of aisles, or other building spacesin a manner that saves energy and provides for adequate worker lighting.While the systems and methods described herein are described withreference to aisle lighting, in some embodiments the systems and methodsmay also be applied to any type of building space where a distinctionbetween a transient motion state and a sustained motion state may bebeneficial. For example, each building space (e.g., rack aisles,specific production spaces, office, storage, shipping, receiving,hallway/traffic, etc.) may be organized into one of three categories(general, task, aisle). In an exemplary embodiment, motion sensed by alighting fixture or a plurality of lighting fixtures are used totransition fixtures from state-to-state automatically and withoutreliance on live user input or a centralized controller. Advantageously,many of the embodiments described herein can therefore operate without100% reliance/uptime on data communication networks or links from thefurthest sensors or lighting fixtures in the building back to acentralized controller.

Each lighting fixture includes processing electronics for causing thelighting fixture to provide increasing levels of illumination inresponse to state changes associated with sensed motion nearby thefixture. In an exemplary embodiment, the processing electronics areconfigured to effect at least three states: (1) a no motion statewherein the lighting fixture is off, providing a minimum level ofillumination, or providing a low level of illumination; (2) a transientmotion or ‘local’ motion state wherein the lighting fixture provides alow-to-medium amount of illumination (e.g., sufficient for safe travelthrough the area); and (3) a sustained motion state wherein the lightingfixture provides a high level of lighting (e.g., a level desirable forsupporting a high level of work productivity and safety).

Referring now to FIGS. 1A-1C, three different states of a lightingfixture 100 are illustrated, according to an exemplary embodiment.Lighting fixture 100 is shown to include a light emitting diode (LED)section 102 and two high intensity fluorescent (HIF) lighting sections104 and 106. It should be appreciated that the methods described hereincould be applied to any type or mixture of lighting technology able toprovide at least three different light levels (low/off, medium, high).In FIG. 1A, lighting fixture 100 is in a no motion state. In the exampleof FIG. 1A, a no motion state results in the entirety of the lightingfixture remaining in a standby mode wherein the HIF sections 104, 106 aswell as the LED section 102 are off. Lighting fixture 100 is illustratedin a transient motion state in FIG. 1B. In the example of FIG. 1B, atransient motion state results in the LED section 102 being ‘on’, whilethe HIF sections 104, 106 are off, to provide a low level ofillumination. Lighting fixture 100 is illustrated in a sustained motionstate in FIG. 1C. In the example of FIG. 1C, a sustained motion stateresults in the HIF sections 104, 106 being on, in addition to the LEDsection 102 being on, to provide a high level of illumination. Lightingfixture 100 further includes a controller 103 configured to controloperation of the lights (e.g., determine the state of the lights) and amotion sensor 105 configured to detect nearby motion and to providecontroller 103 with motion information.

In some embodiments, the transient motion state is entered when localmotion (e.g., motion actually sensed by a motion sensor local to alighting fixture) is detected but the local motion has not yet beensustained for a period of time (which would result in a sustained motionstate). In the present disclosure, the phrase ‘a local motion state’ and‘a transient motion state’ may be used interchangeably and refer to thesame state.

Referring now to FIG. 2A, a perspective overhead view of an exemplarylighting fixture 200 is illustrated, according to an exemplaryembodiment. Lighting fixture 200 does not include an LED section such asthat shown in FIGS. 1A-1C, but lighting fixture 200 can provide at leastthe same three lighting states (i.e., low/off light associated with a nomotion state, medium/intermediate illumination associated with atransient motion state, and a relatively high level of illuminationassociated with a sustained motion state) by step-dimming its HIFballast 202 and lamps 208.

Lighting fixture 200 is shown to include a frame 206 that holds theballast 202 and a plurality of lamps 208. Frame 206 can be coupled toone or more brackets, rails, hooks, or other mechanisms for holdingframe 206 and therefore lighting fixture 200 in place for use. Ballast202 is coupled to controller 204. Controller 204 includes processingelectronics for controlling the state changes and lighting fixturebehavior during the different states. Controller 204 is shown to includemotion sensor 210. Controller 204 is configured to change states basedon motion sensed by motion sensor 210.

Referring now to FIG. 2B, a diagram of a facility lighting system 250for use with lighting fixture 100 shown in FIGS. 1A-C and/or lightingfixture 200 shown in FIG. 2A is illustrated, according to an exemplaryembodiment. Facility lighting system 250 is shown to include controlcomputer 252 that is configured to conduct configuration and controlactivities relative to multiple lighting fixtures' controllers such ascontroller 103 of FIGS. 1A-C or controller 204 of FIG. 2A. While controlcomputer 252 is shown in FIG. 2B, it should be appreciated that thelighting fixtures themselves includes electronics for conducting theoccupancy/motion-based state transitions. Therefore, control computer252 is not required in many exemplary embodiments. If control computer252 is provided, it may be used to provide user interfaces for allowinga user to change zone boundaries, lighting schedules, default settingsor to make other configuration/administrative changes.

Control computer 252 is configured to provide a graphical user interfaceto a local or remote electronic display screen for allowing a user toadjust configuration or control parameters, turn lighting fixtures on oroff, change the motion sensitive modes assigned to a group or zone oflighting fixtures, or to otherwise affect the operation of lightingfixtures in a facility. For example, control computer 252 is shown toinclude touch screen display 254 for displaying such a graphical userinterface and for allowing user interaction (e.g., input and output)with control computer 252. Various exemplary graphical user interfacesfor display on touch screen display 254 and control activitiesassociated therewith are described in greater detail in application Ser.No. 12/550,270, assigned to Orion Energy Systems, Inc and titled“Lighting Fixture Control Systems and Methods.” While control computer252 is shown as housed within a wall-mountable panel, control computer252 may alternatively be housed in or coupled to any other suitablecomputer casing or frame. In an exemplary embodiment, user interfacesprovided by control computer 252 and display 254 allow users toreconfigure or reset aspects of the lighting system.

Referring further to FIG. 2B, control computer 252 is shown as connectedto master transceiver 258 via communications interface 256. Mastertransceiver 258 may be a radio frequency transceiver configured toprovide wireless signals to a network of controllers such as controller204. In FIG. 2B, master transceiver 258 is shown in bi-directionalwireless communication with a plurality of lighting fixture controllers261, 262, 271, and 272. FIG. 2B further illustrates controllers 261 and262 forming a first logical group 260 identified as “Zone I” andcontrollers 271 and 272 forming a second logical group 270 identified as“Zone II.” Control computer 252 is configured to provide differentprocessing, different commands, or different modes for “Zone I” relativeto “Zone II.” While control computer 252 is configured to complete avariety of control activities for lighting fixture controllers 261, 262,271, 272, in many exemplary embodiments of the present disclosure, eachcontroller associated with a lighting fixture (e.g., controllers 261,262, 271, 272) includes circuitry configured to provide a variety of“smart” or “intelligent features” that are either independent of controlcomputer 252 or operate in concert with control computer 252. A detailedblock diagram of such a controller is shown in FIG. 3.

Referring now to FIG. 3, a detailed block diagram of controller 204 isshown, according to an exemplary embodiment. Controller 204 is generallyconfigured to include circuitry configured with an algorithm to controlon/dim/off cycling of connected lighting fixtures, an algorithm to logusage information for the lighting fixture, an algorithm configured toprevent premature restrikes to limit wear on the lamps and ballast,and/or other algorithms for allowing controller 204 to send and receivecommands or information to/from other peer devices (e.g., other lightingfixture controllers) or to/from the master controller.

Controller 204 is shown to include power relays R1 and R2 configured tocontrollably switch on, increase, decrease, or switch off high voltagepower outputs that may be provided to a first ballast (e.g., a ballastfor HIF lamps) and a second ballast (e.g., a ballast for a set of LEDs).In other exemplary embodiments, power relays R1, R2 may be configured toprovide a low voltage control signal, optical signal, or otherwise tothe lighting fixture which may cause one or more ballasts, lamps, and/orcircuits of the lighting fixture to turn on, dim, or turn off.

As power relays R1 and R2 are configured to provide high voltage powerswitching to varying lighting fixture ballasts, controller 204 andrelays R1/R2 may include a port, terminal, receiver, or other input forreceiving power from a high voltage power source. In embodiments where arelatively low voltage or no voltage control signal (e.g., optical) isprovided from relays R1, R2, power for circuitry of controller 204 maybe received from a power source provided to the lighting fixtures orfrom another source. In any embodiment of controller 204, appropriatepower supply circuitry (e.g., filtering circuitry, stabilizingcircuitry, etc.) may be included with controller 204 to provide power tothe components of controller 204 (e.g., relays R1 and R2).

Referring still to FIG. 3, controller 204 is shown to include processingelectronics 300. Processing electronics 300 generally utilizeselectronics circuits and components (e.g., control circuits, relays,etc.) to effect the control activities described herein. In the exampleshown in FIG. 3, processing electronics 300 is embodied as a circuit(spread over one or more printed circuit boards) including controlcircuit 304. Control circuit 304 receives and provides data or controlsignals from/to power relays R1 and R2 and sensor circuit 310. Controlcircuit 304 is configured to cause one or more lamps of the lightingfixture to turn on and off (or dim) via control signals sent to powerrelays R1 and R2. For example, control circuit 304 can make adetermination that an “on” or “off” signal should be sent to powerrelays R1 or R2 based on inputs received from wireless controller 305 orsensor circuit 310. By way of another example, a command to turn thelighting fixture “off” may be received at wireless transceiver 306 andinterpreted by wireless controller 305. Upon recognizing the “off”command, wireless controller 305 provides an appropriate control signalto control circuit 304 which causes control circuit 304 to switch one ormore of power relays R1, R2 off Similarly, when sensor circuit 310including sensor 210 experiences an environmental condition, logicmodule 314 may determine whether or not controller 204 and controlcircuit 304 should change “on/off” states of one or more of the relaysR1, R2. For example, if motion is detected by sensor 210 and sensorcircuit 310, logic module 314 may determine that control circuit 304should change states such that power relay R1 is “on.” If sustainedmotion is detected by sensor 210 and sensor circuit 310, logic module314 may determine that control circuit 304 should change states suchthat power relay R2 is “on” in addition to power relay R1 (providing ahigh level of illumination on the sustained motion activity). Othercontrol decisions, logic and activities provided by controller 204 andthe components thereof are described below and with reference to otherFigures.

When or after control decisions based on sensor 210 or commands receivedat wireless transceiver 306 are made, in some exemplary embodiments,logic module 314 is configured to log usage information for the lightingfixture in memory 316. For example, if control circuit 304 causes powerrelays R1 and R2 to change states such that the lighting fixture turnson or off, control circuit 304 may inform logic module 314 of the statechange and logic module 314 may log usage information based on theinformation from control circuit 304. The form of the logged usageinformation can vary for different embodiments. For example, in someembodiments, the logged usage information includes an event identifier(e.g., “on”, “off”, cause for the state change, etc.) and a timestamp(e.g., day and time) from which total usage may be derived. In otherembodiments, the total “on” time for the lighting fixture (or lamp set)is counted such that only an absolute number of hours that the lamp hasbeen on (for whatever reason) has been tracked and stored as the loggedusage information. In addition to logging or aggregating temporalvalues, each logic module 314 may be configured to process usageinformation or transform usage information into other values orinformation. For example, in some embodiments, time-of-use informationis transformed by logic module 314 to track the energy used by thelighting fixture (e.g., based on bulb ratings, known energy draw of thefixture in different on/off/partial on modes, etc.). In someembodiments, each logic module 314 will also track how much energysavings the lighting fixture is achieving relative to a conventionallighting fixture, conventional control logic, or relative to anotherdifference or change of the lighting fixture. For the purposes of manyembodiments of this disclosure, any such information relating to usagefor the lighting fixture may be considered logged “usage information.”In other embodiments, the usage information logged by module 314 islimited to on/off events or temporal aggregation of on states; in suchembodiments energy savings calculations or other calculations may becompleted by control computer 252 or another remote device.

In an exemplary embodiment, controller 204 (e.g., via wirelesstransceiver 306) is configured to transmit the logged usage informationto remote devices such as control computer 252. Wireless controller 305may be configured to recall the logged usage information from memory 316at periodic intervals (e.g., every hour, once a day, twice a day, etc.)and to provide the logged usage information to wireless transceiver 306at the periodic intervals for transmission back to control computer 252.In other embodiments, control computer 252 (or another network device)transmits a request for the logged information to wireless transceiver306 and the request is responded to by wireless controller 305 bytransmitting back the logged usage information. In a preferredembodiment a plurality of controllers such as controller 204asynchronously collect usage information for their fixture and controlcomputer 252, via request or via periodic transmission of theinformation by the controllers, gathers the usage information for lateruse.

Wireless controller 305 may also be configured to handle situations orevents such as transmission failures, reception failures, and the like.Wireless controller 305 may respond to such failures by, for example,operating according to a retransmission scheme or another transmitfailure mitigation scheme. Wireless controller 305 may also control anyother modulating, demodulating, coding, decoding, routing, or otheractivities of wireless transceiver 306. For example, controller 204′scontrol logic (e.g., controlled by logic module 314 and/or controlcircuit 304) may periodically include making transmissions to othercontrollers in a zone, making transmissions to particular controllers,or otherwise. Such transmissions can be controlled by wirelesscontroller 305 and such control may include, for example, maintaining atoken-based transmission system, synchronizing clocks of the various RFtransceivers or controllers, operating under a slot-basedtransmission/reception protocol, or otherwise.

Referring still to FIG. 3, sensor 210 may be an infrared sensor, anoptical sensor, a camera, a temperature sensor, a photodiode, a carbondioxide sensor, or any other sensor configured to sense environmentalconditions such as a lighting level or human occupancy of a space. Forexample, in one exemplary embodiment, sensor 210 is a motion sensor andlogic module 314 is configured to determine whether control circuit 304should change states (e.g., change the state of power relays R1 and R2)based on whether motion is detected by sensor 210 (e.g., detected motionreaches or exceeds threshold value). In the same or other embodiments,logic module 314 may be configured to use the signal from the sensor 210to determine an ambient lighting level. Logic module 314 may thendetermine whether to change states based on the ambient lighting level.For example, logic module 314 may use a condition such as time of day inaddition to ambient lighting level to determine whether to turn thelighting fixture off or on. During a critical time of the day (e.g.,when a staffed assembly line is moving), even if the ambient lightinglevel is high, logic module 314 may refrain from turning the lightingfixture off. In another embodiment, by way of further example, logicmodule 314 is configured to provide a command to control circuit 304that is configured to cause control circuit 304 to turn the one or morelamps of the fluorescent lighting fixture on when logic module 314detects motion via the signal from sensor 210 and when logic circuit 314determines that the ambient lighting level is below a thresholdsetpoint.

Referring yet further to FIG. 3, control circuit 304 is configured toprevent damage to lamps 108 or 110 from manual or automatic controlactivities. Particularly, control circuit 304 may be configured toprevent on/off cycling of sections 102, 104, 106 by holding the lamps ofthe sections in an “on” state for a predefined period of time (e.g.,thirty minutes, fifteen minutes, etc.) even after the condition thatcaused the lamp to turn on is no longer true. Accordingly, if, forexample, motion or a low ambient lighting level causes control circuit304 to turn sections 102, 104, and/or 106 on but then the motion and/orambient lighting level suddenly increases (a worker enters the zone orthe sun comes out), control circuit 304 may keep the lamps on (eventhough the ‘on’ condition expired) for a predetermined period of time sothat the lamps are taken through their preferred cycle. Similarly, in analternative embodiment, control circuit 304 may be configured to holdthe lamp in an “off” state for a predefined period of time since thelamp was last turned off to ensure that the lamp is given time to coolor otherwise settle after the last “on” state.

Referring yet further to FIG. 3, logic module 314 or control circuit 304may be configured to include a re-strike violation module (e.g., inmemory 316) that is configured to prevent logic module 314 fromcommanding control circuit 304 to cause the fluorescent lamps to turn onwhile a re-strike time is counted down. The re-strike time maycorrespond with a maximum cool-down time for the lamp, allowing the lampto experience its preferred strike-up cycle even if a command to turnthe lamp back on is received at wireless transceiver 306. In otherembodiments, logic module 314 or control circuit 304 may be configuredto prevent rapid on/off switching due to sensed motion, anotherenvironmental condition, or a sensor or controller error. Logic module314 or control circuit 304 may be configured to, for example, entirelydiscontinue the on/off switching based on inputs received from sensor210 by analyzing the behavior of the sensor, the switching, and loggedusage information. By way of further example, logic circuit 314 orcontrol circuit 304 may be configured to discontinue the on/offswitching based on a determination that switching based on the inputsfrom the sensor has occurred too frequently (e.g., exceeding a thresholdnumber of “on” switches within a predetermined amount of time, undesiredswitching based on the time of day or night, etc.). Logic module 314 orcontrol circuit 304 may be configured to log or communicate such adetermination. Using such configurations, logic module 314 and/orcontrol circuit 304 are configured to self-diagnose and correctundesirable behavior that would otherwise continue occurring based onthe default, user, or system-configured settings.

According to one embodiment, a self-diagnostic feature would monitor thenumber of times that a fixture or device was instructed to turn on (oroff) based upon a signal received from a sensor (e.g. motion, ambientlight level, etc.). If the number of instructions to turn on (or off)exceeded a predetermined limit during a predetermined time period, logicmodule 314 and/or control circuit 304 could be programmed to detect thatthe particular application for the fixture or device is not well-suitedto control by such a sensor (e.g. not an optimum application for motioncontrol or ambient light-based control, etc.), and would be programmedto disable such a motion or ambient light based control scheme, andreport/log this action and the basis. For example, if the algorithm isbased on more than four instructions to turn on (or off) in a 24 hourperiod, and the number of instructions provided based on signals fromthe sensor exceeds this limit within this period, the particularsensor-based control function would be disabled, as not being optimallysuited to the application and a notification would be logged andprovided to a user or facility manager. Of course, the limit and timeperiod may be any suitable number and duration intended to suit theoperational characteristics of the fixture/device and the application.In the event that a particular sensor-based control scheme in aparticular zone is disabled by the logic module and/or control circuit,the fixture or device is intended to remain operational in response toother available control schemes (e.g. other sensors, time-based, userinput or demand, etc.). The data logged by the logic module and/orcontrol circuit may also be used in a ‘learning capacity’ so that thecontrols may be more optimally tuned for the fixtures/devices in aparticular application and/or zone. For example, the logic module and/orcontrol circuit may determine that disablement of a particularsensor-based control feature occurred due to an excessive number ofinstructions to turn on (or off) based on signals from a particularsensor that occurred within a particular time window, and may bereprogrammed to establish an alternate monitoring duration that excludesthis particular time window for the particular sensor-based controlscheme to ‘avoid’ time periods that are determined to be problematic.This ability to learn or self-update is intended to permit the system toadjust itself to update the sensor-based control schemes to differenttime periods that are more optimally suited for such a control scheme,and to avoid time periods that are less optimum for such a particularsensor-based control scheme.

Referring now to FIG. 4, a more detailed block diagram of controlcomputer 252 is shown, according to an exemplary embodiment. Controlcomputer 252 may be configured as the “master controller” described inU.S. application Ser. No. 12/240,805, filed Sep. 29, 2008, andincorporated herein by reference in its entirety. Control computer 252is generally configured to receive user inputs (e.g., via touchscreendisplay 254) and to set or change settings of lighting system 250 basedon the user inputs.

Referring further to FIG. 4, control computer 252 is shown to includeprocessing circuit 402 including memory 404 and processor 406. In anexemplary embodiment, control computer 252 and more particularlyprocessing circuit 402 are configured to run a Microsoft WindowsOperating System (e.g., XP, Vista, etc.) and are configured to include asoftware suite configured to provide the features described herein. Thesoftware suite may include a variety of modules (e.g., modules 408-414)configured to complete various activities of control computer 252.Modules 408-414 may be or include computer code, analog circuitry, oneor more integrated circuits, or another collection of logic circuitry.In various exemplary embodiments, processor 406 may be a general purposeprocessor, a specific purpose processor, a programmable logic controller(PLC), a field programmable gate array, a combination thereof, orotherwise and configured to complete, cause the completion of, and/orfacilitate the completion of the activities of control computer 252described herein. Memory 404 may be configured to store historical datareceived from lighting fixture controllers or other building devices,configuration information, schedule information, setting information,zone information, or other temporary or archived information. Memory 404may also be configured to store computer code for execution by processor406. When executed, such computer code (e.g., stored in memory 404 orotherwise, script code, object code, etc.) configures processing circuit402, processor 406 or more generally control computer 252 for theactivities described herein.

Touch screen display 254 and more particularly user interface module 408are configured to allow and facilitate user interaction (e.g., input andoutput) with control computer 252. It should be appreciated that inalternative embodiments of control computer 252, the display associatedwith control computer 252 may not be a touch screen, may be separatedfrom the casing housing the control computer, and/or may be distributedfrom the control computer and connected via a network connection (e.g.,Internet connection, LAN connection, WAN connection, etc.). Further, itshould be appreciated that control computer 252 may be connected to amouse, keyboard, or any other input device or devices for providing userinput to control computer 252. Control computer 252 is shown to includea communications interface 256 configured to connect to a wireassociated with master transceiver 258.

Communications interface 256 may be a proprietary circuit forcommunicating with master transceiver 258 via a proprietarycommunications protocol. In other embodiments, communications interface256 may be configured to communicate with master transceiver 258 via astandard communications protocol. For example, communications interface256 may include Ethernet communications electronics (e.g., an Ethernetcard) and an appropriate port (e.g., an RJ45 port configured for CAT5cabling) to which an Ethernet cable is run from control computer 252 tomaster transceiver 258. Master transceiver 258 may be as described inU.S. application Ser. Nos. 12/240,805, 12/057,217, or 11/771,317, whichare each incorporated herein by reference. Communications interface 256and more generally master transceiver 258 are controlled by logic ofwireless interface module 412. Wireless interface module 412 may includedrivers, control software, configuration software, or other logicconfigured to facilitate communications activities of control computer252 with lighting fixture controllers. For example, wireless interfacemodule 412 may package, address format, or otherwise prepare messagesfor transmission to and reception by particular controllers or zones.Wireless interface module 412 may also interpret, route, decode, orotherwise handle communications received at master transceiver 258 andcommunications interface 256.

Referring still to FIG. 4, user interface module 408 may include thesoftware and other resources for the handling of automatic or userinputs received at the graphical user interfaces of control computer252. While user interface module 408 is executing and receiving userinput, user interface module 408 may interpret user input and causevarious other modules, algorithms, routines, or sub-processes to becalled, initiated, or otherwise affected. For example, control logicmodule 414 and/or a plurality of control sub-processes thereof may becalled by user interface module 408 upon receiving certain user inputevents. User interface module 408 may also be configured to includeserver software (e.g., web server software, remote desktop software,etc.) configured to allow remote access to touch screen display 254.User interface module 408 may be configured to complete some of thecontrol activities described herein rather than control logic module414. In other embodiments, user interface module 408 merely drives thegraphical user interfaces and handles user input/output events whilecontrol logic module 414 controls the majority of the actual controllogic.

Control logic module 414 may be the primary logic module for controlcomputer 252 and may be the main routine that calls, for example,modules 408, 410, etc. Control logic module 414 may generally beconfigured to provide lighting control, energy savings calculations,demand/response-based control, load shedding, load submetering, HVACcontrol, building automation control, workstation control, advertisementcontrol, power strip control, “sleep mode” control, or any other typesof control. In an exemplary embodiment, control logic module 414operates based off of information stored in one or more databases ofcontrol computer 252 and stored in memory 404 or another memory devicein communication with control computer 252. The database may bepopulated with information based on user input received at graphicaluser interfaces and control logic module 414 may continuously draw onthe database information to make control decisions. For example, a usermay establish any number of zones, set schedules for each zone, createambient lighting parameters for each zone or fixture, etc. Thisinformation is stored in the database, related (e.g., via a relationaldatabase scheme, XML sets for zones or fixtures, or otherwise) andrecalled by control logic module 414 as control logic module 414proceeds through its various control algorithms.

Control logic module 414 may include any number of functions orsub-processes. For example, a scheduling sub-process of control logicmodule 414 may check at regular intervals to determine if an event isscheduled to take place. When events are determined to take place, thescheduling sub-process or another routine of control logic module 414may call or otherwise use another module or routine to initiate theevent. For example, if the schedule indicates that a zone should beturned off at 5:00 pm, then when 5:00 pm arrives the schedulingsub-process may call a routine (e.g., of wireless interface module) thatcauses an “off” signal to be transmitted by master transceiver 258.Control logic module 414 may also be configured to conduct or facilitatethe completion of any other process, sub-process, or process stepsconducted by control computer 252 described herein.

Referring further to FIG. 4, device interface module 410 facilitates theconnection of one or more field devices, sensors, or other inputs notassociated with master transceiver 258. For example, fieldbus interfaces416 and 420 may be configured to communicate with any number ofmonitored devices 418 and 422. The communication may be according to acommunications protocol which may be standard or proprietary and/orserial or parallel. Fieldbus interfaces 416, 420 can be or includecircuit cards for connection to processing circuit 402, jacks orterminals for physically receiving connectors from wires couplingmonitored devices 418 and 422, logic circuitry or software fortranslating communications between processing circuit 402 and monitoreddevices 418 and 422, or otherwise. In an exemplary embodiment, deviceinterface module 410 handles and interprets data input from themonitored devices and controls the output activities of fieldbusinterfaces 416 and 420 to monitored devices 418 and 422.

Fieldbus interfaces 416 and 420 and device interface module 410 may alsobe used in concert with user interface module 408 and control logicmodule 414 to provide control to the monitored devices 418 and 422. Forexample, monitored devices 418 and 422 may be mechanical devicesconfigured to operate a motor, one or more electronic valves, one ormore workstations, machinery stations, a solenoid or valve, orotherwise. Such devices may be assigned to zones similar to the lightingfixtures described above and below or controlled independently. Userinterface module 408 may allow schedules and conditions to beestablished for each of devices 418 and 422 so that control computer 252may be used as a comprehensive energy management system for a facility.For example, a motor that controls the movement of a spinningadvertisement may be coupled to the power output or relays of acontroller very similar if not identical to controller 204. Thiscontroller may be assigned to a zone (e.g., via user interfaces attouchscreen display 254) and provided a schedule for turning on and offduring the day. In another embodiment, the electrical relays of thecontroller may be coupled to other building devices such as videomonitors for informational display, exterior signs, task lighting, audiosystems, or other electrically operated devices.

Referring further to FIG. 4, power monitor 450 is shown as coupled tofieldbus interfaces 416 in an exemplary embodiment. However, powermonitor 450 may also or alternatively be coupled to its own controlleror RF transceiver 451 for communicating with master transceiver 258.Power monitor 450 may generally be configured to couple to buildingpower resources (e.g., building mains input, building power meter, etc.)and to receive or calculate an indication of power utilized by thebuilding or a portion of the building. This input may be received in avariety of different ways according to varying embodiments. For example,power monitor 450 may include a current transformer (CT) configured tomeasure the current in the mains inlet to a building, may be coupled toor include a pulse monitor, may be configured to monitor voltage, or maymonitor power in other ways. Power monitor 450 is intended to provide“real time” or “near real time” monitoring of power and to provide theresult of such monitoring to control computer 252 for use or reporting.When used with power monitor 450, control logic module 414 may beconfigured to include logic that sheds loads (e.g., sends off signals tolighting fixtures via a lighting fixture controller network, sends offsignals to monitored devices 418 and 422, adjusts ambient lightsetpoints, adjusts schedules, shuts lights off according to a prioritytier, etc.) to maintain a setpoint power meter level or threshold. Inother exemplary embodiments, control logic module 414 may store orreceive pricing information from a utility and shed loads if the meteredpower usage multiplied by the pricing rate is greater than certainabsolute thresholds or tiered thresholds. For example, if daily energycost is expected to exceed $500 for a building, control logic module 414may be configured to change the ambient light setpoints for the lightingfixtures in the building until daily energy cost is expected to fallbeneath $500. In an exemplary embodiment, user interface module 408 isconfigured to cause a screen to be displayed that allows a user toassociate different zones or lighting fixtures with differentdemand/response priority levels. Accordingly, a utility provider orinternal calculation determines that a load should be shed, controllogic module 414 will check the zone or lighting fixture database toshed loads of the lowest priority first while leaving higher priorityloads unaffected.

Referring now to FIG. 5, an exemplary control activity for a system ofcontrollers as described herein is illustrated, according to anexemplary embodiment. As described in FIG. 2B, lighting fixtures (ormore particularly controllers for lighting fixtures) can be grouped intozones. Rather than reporting motion, ambient light, or other sensedconditions back to master transceiver 258 for processing or action,controllers such as controller 204 may be configured to broadcastcommands or conditions to other RF transceivers coupled to othercontrollers in the same zone. For example, in FIG. 5, lighting zone Iincludes four controllers. When motion is detected by sensor 210 ofcontroller 204, logic module 314 and/or control circuit 304 causeswireless transceiver 306 to transmit an indication that motion wasdetected by the sensor. Accordingly, control circuits of the controllersreceiving the indication can decide whether or not to act upon theindication of motion. The RF signals including an indication of motionmay also include a zone identifier that receiving controllers can use todetermine if the signal originated from their zone or another zone. Inother exemplary embodiments, controller 204 may address messages toparticular controllers (e.g., the addresses of neighbors or theaddresses of other controllers in the zone). Logic module 314 mayfurther be configured to cause the radio frequency transceiver totransmit commands to other radio frequency transceivers coupled to otherfluorescent lighting fixtures. For example, logic module 314 and/orcontrol circuit 304 may be configured to interpret a signal received atthe radio frequency transceiver as indicating that motion was detectedby another device in the zone. In an exemplary embodiment of thelighting fixture controller, some will be configurable as relay devicesand when so configured, will relay any commands or information thecontroller receives from other zone controllers. Controller 504 isillustrated to be configured as such a relay device. When controller 504receives broadcast 500 indicating motion from controller 261, controller504 relays broadcast 500 via transmission 502 to other zone devices(e.g., controller 506). This way, an event such as motion can bepropagated to each of the lighting fixtures in a zone without networktraffic to controller 261 and/or without necessitating direct control ofthe lighting fixtures by controller 261. This activity may beconfigurable (e.g., via a GUI provided by control computer 252) so thatonly some controllers are relays, all controllers are relays, or so thatno controllers are relays and only devices within range of the detectingcontroller act on its broadcasts. Further, the relay or rebroadcast canbe address-based or more similar to a true broadcast. For example, in anaddress-based relay, the controller serving as a relay may know theaddresses of certain network controllers to which to transmit therelayed information. In another example, the broadcast may be generaland not addressed to any particular controller, controllers, or zone.

To implement zone control activities, each controller may be configuredto store a lighting zone value in memory (e.g., memory 316). This valuemay be used, for example, to determine whether another device sending acommand is associated with the lighting zone value stored in memory. Forexample, controller 271 may include a lighting zone value of “II” inmemory and controller 261 may include data representative of controller261′s lighting zone value (e.g., “I”) with its transmission indicatingthat motion was detected. When controller 271 receives the lighting zonevalue, controller 271 (e.g., a control circuit or logic circuit thereof)may compare “I” and “II” and make a determination that controller 271will not act on the received indication of motion (i.e., controller 271leaves its relays off while all of the controllers in zone I switchtheir relays on).

Referring now to FIG. 6, a flow chart of a process 600 for controllingmultiple lighting fixtures in a zone based on sensor input is shown,according to an exemplary embodiment. Process 600 is shown to includereceiving signals from a sensor (e.g., sensor 210) coupled to a firstcontroller for a first zone (step 602). Once received, circuitry of thefirst controller can determine whether the received signals represent anevent that should be acted upon (e.g., by changing lighting states,etc.) in the first zone (step 604). Process 600 is further shown toinclude using circuitry of the first controller to transmit a commandand/or an indication of the event with a first zone identifier (step606). The transmission is received by a controller in a second zone.Circuitry of the controller in the second zone determines that thetransmission is for another zone and does not act on the receivedtransmission (step 608). The transmission may also be received by asecond controller for the first zone (step 610). Circuitry of the secondcontroller for the first zone inspects the received transmission andacts on the information of the transmission when the controllerdiscovers that its stored zone identifier matches the received zoneidentifier (step 612). The second controller for the first zone may alsobe configured as a relay node and to retransmit the received command orindication to other first zone controllers (e.g., controller 506).

FIG. 7 illustrates how different lighting zones may be organized withina building having aisles. In the example of FIG. 7, building entrance704 is shown to include two lighting fixtures (labeled with Az7 in theillustration) assigned to a ‘general’ mode of operation and zone 7 ofthe building. Production area 706 of the building is shown to includefive lighting fixtures (labeled with Tz8 in the illustration) assignedto a ‘task’ mode of operation and zone 8 of the building. High trafficwork area 740 of the building includes some lighting fixtures set in ageneral mode of operation and others set in a task mode of operation(the lighting fixtures in a task mode of operation and associated zone 9are labeled Tz9 in the illustration of FIG. 7 and the lighting fixturesin the general mode of operation and associated with zone 9 are labeledAz9).

The illustration of FIG. 7 further illustrates three aisles. Each aisleis shown as divided into two zones, a small forward zone near the frontof the aisle (i.e., near the high traffic work area of the building) anda larger zone behind the small forward zone. Items that need to befrequently accessed may be placed in the small forward zone near thefront of the aisle, while items that are less frequently accessed may beplaced in the larger zone. Referring to aisle portion 710, two lightingfixtures are shown as installed within the aisle portion (labeled withAz1 in the illustration) and assigned to an ‘aisle’ mode of operationand zone 1 of the building. Referring to aisle portion 701, six lightingfixtures are shown as installed within the aisle portion (labeled withAz2 in the illustration) and assigned to an ‘aisle’ mode of operationand zone 2 of the building. Referring to aisle portion 720, two lightingfixtures are shown as installed within the aisle portion (labeled withAz3 in the illustration) and assigned to an ‘aisle’ mode of operationand zone 3 of the building. Referring further to aisle portion 702, sixlighting fixtures are shown as installed within the aisle portion(labeled with Az4 in the illustration) and assigned to an ‘aisle’ modeof operation and zone 4 of the building. Referring to aisle portion 730,two lighting fixtures are shown as installed within the aisle portion(labeled with Az5 in the illustration) and assigned to an ‘aisle’ modeof operation and zone 5 of the building. Referring to aisle portion 703,six lighting fixtures are shown as installed within the aisle portion(labeled with Az6 in the illustration) and assigned to an ‘aisle’ modeof operation and zone 6 of the building. The general, task, and aislemodes of operation for a lighting fixture are described with referenceto subsequent Figures.

Referring now to FIG. 8, a flow chart of a process 800 for providing anaisle mode of operation is shown. While a process 800 is illustrated anddescribed with particularity, it should be noted that many differenttimings, checks, step orders, or other variations are contemplated andmay fall within the scope of one or more appended claims. Process 800can be executed by processing electronics 300 of controller 204 shown inFIG. 3 or by other processing electronics coupled to a lighting fixture.In an alternative embodiment, process 800 can be partially or entirelyexecuted by processing electronics remote from the lighting fixture(e.g., a control computer 252). For example, in an alternativeembodiment, some of the steps of process 800 may be executed by alighting fixture's local controller and other of the steps of process800 may be executed by control computer 252.

Process 800 is shown to begin at step 802 where timers or counters T1through T5 are initially set to zero (step 802). Timers or counters T1through T5 are variously used to control the timing of transitions intoand out of varying lighting states. T1 represents a time period forwhich dim illumination should be provided by the lighting fixture. T2represents a time period for which high illumination should be providedby the lighting fixture. T3 and T4 represent time periods which are usedto represent periods of time where sustained local motion is detected.T5 represents a time period for which local motion has occurred. Whileparticular timings are described with reference to process 800 and theother processes described herein, different state timings may beassociated with varying exemplary embodiments.

At step 804, the primary aisle mode loop begins. It should be notedthat, prior to starting the primary aisle mode loop at step 804, anynumber of additional steps may be conducted to warm up the lamp, conductdaily lamp “seasoning”, or to conduct another start-up task. Forexample, the initial motion detected in a zone during a day may resultin all lamps within the zone being turned high for one minute to ensurethe daily lamp seasoning.

Once the loop is begun, process 800 can begin continually checking forwhether local motion is detected (step 806). As described above withreference to FIG. 3, and according to an exemplary embodiment, sensorcircuit 310 and sensor 210 can process infrared video signals toestimate whether significant movement (e.g., enough to be a human ratherthan a small animal) is occurring in the space covered by the sensor210's sensor detection signal. In response to local motion beingdetected, activities including switching relay R1 (e.g., shown in FIG.3) to be “on” to provide relatively ‘dim’ illumination from the lightingfixture are completed (step 808). In step 808, timer T1 is set/reset toequal 90 seconds. In step 808, also in response to the detection oflocal motion, the processing electronics of the lighting fixture (e.g.,processing electronics 304 shown in FIG. 3) causes a communicationsinterface (e.g., transceiver 306 of FIG. 3, a wired communicationsinterface) to transmit a zone motion message to other lighting fixturecontrollers in the zone. Each time local motion is detected, T5 is resetto equal 3 seconds. It should be noted that relay R1 will stay ‘on’while local motion is being detected. As will be noted below, becausetimer T1 is reset to 90 seconds each time local motion is detected, thelighting fixture will provide dim illumination for at least ninetyseconds after local motion is detected.

At step 810, a check is conducted for whether T4 is greater than 0seconds. T4 is used as a dwell timer such that a number of seconds(e.g., 2) can pass before the process 800 resets timer T3 that is usedfor checking whether the local motion is sustained in step 812. If T4 isnot greater than zero seconds according to the check at step 810, T3 isreset to equal 6 seconds and T4 is reset to equal 2 seconds (step 814).If T4 is greater than zero seconds (meaning that motion has beendetected within the T4 dwell time), then step 812 checks for whether thelocal motion has been sustained for a predetermined period of time(e.g., 6 seconds). In other words, step 812 checks for whether T3 hasbeen counted down from 6 to zero.

If step 812 results in a determination that local motion has beensustained, then T4 is reset to 2 seconds at step 816. Further, inresponse to sustained local motion, relay R2 is caused to be ‘on’providing a ‘high’ illumination level. T2 is reset to thirty seconds anda sustained motion message is transmitted from transceiver 306. As willbe explained below, when T2 counts down to zero, relay R2 isdeactivated. Therefore, in response to detected sustained local motion(e.g., detecting movement associated with a worker concentrating onmaking a product pull in an aisle location for longer than 6 seconds),the lighting fixture is caused to switch from a dim illumination stateto a high or bright illumination state—providing the highest possiblelight level for the worker in the aisle. If local motion does notcontinue, the lighting fixture returns to a dim state after time T2expires, saving energy when high illumination is no longer required dueto worker activity.

At step 820, process 800 decrements all non-zero timers other than T4 byone. Steps 822 and 824 check for the expiration of timer T1 and T2,respectively. As described above, if T2 has expired, then (at step 828)relay R2 is deactivated to reduce the illumination level from high todim (e.g., where T1 only is activated). If T1 has expired, then (at step826) relay R1 is deactivated to reduce the illumination level from dimto off (or lower). After state changes at steps 826, 828, or afterconsecutive ‘no’ decisions at step 822, 824, the loop repeats at step804.

As shown in FIG. 8, if local motion is not detected at step 806, then T4is decremented by one (if T4 is not already zero) at step 830. At step832, process 800 includes checking for whether a sustained motionreceived message has been received from a linked or nearby lightingfixture (e.g., a lighting fixture within the same zone). Step 832 alsochecks for whether T5 is greater than 0. If T5 is greater than zero,local motion has recently been detected by the lighting fixture at step806. Accordingly, step 832 essentially checks for whether sustainedmotion is happening nearby and whether local motion has recentlyoccurred (e.g., with in the last 5 seconds). If so, then relay R2 isswitched on to provide a high illumination level at step 818. T2 isreset to 30 seconds such that the high level of illumination will beprovided for at least 30 seconds. Further, transceiver 306 is caused torebroadcast a sustained motion message to the zone.

If a sustained motion message is not received at step 832 (or T5 is zerowhen the sustained motion message is received), then a check isconducted for whether zone motion has been received (step 834). A zonemotion message is a message from another lighting fixture's transceiverin the zone indicating that motion (but not sustained motion) wasdetected by the transmitting fixture's motion sensor. If the loop hasprogressed to step 834 and no zone motion has been received, then step820 is reached without further state changes and the loop continues asdescribed above. If a zone motion message has been received during acycle of the loop at step 834, then relay R1 is switched on to provide adim illumination level (step 836). At step 836, T1 is also reset toequal 90 seconds and the received zone motion message is retransmittedto the rest of the zone. Step 820 is then reached and the loopcontinues.

Because of the activity of steps 834, 836, when transient motion isdetected in an aisle or other zone, the entire zone illuminates at a dimlevel for at least 90 seconds. Such activity ensures a worker making aquick trip to the zone will at least have a dim level of light. If anysustained motion is detected (e.g., at step 812), then a bubble of light(i.e., high illumination) is formed around the worker's sustainedmotion. In other words, the fixture that detects the local motion isswitched to high illumination at step 818. Further, the fixture thatdetects the local motion transmits (i.e., blasts) a sustained localmotion message at step 818. Nearby fixtures that have detected motionwithin the last 5 seconds and receive the sustained local motion messageare also switched to high illumination. In an exemplary embodiment, someamount of motion sensor overlap may be provided or desired so that twoor more lighting fixtures typically switch to high illumination whensustained motion is occurring.

Advantageously, the process 800 shown in FIG. 8 can save energy relativeto conventional lighting system that are timer-based. Further, FIG. 8can provide for varying levels of illumination depending on the activityin particular spaces—providing safety to workers that are locallyworking on a project for longer than 6 seconds, but saving energy byrefraining from turning all of the lights in the zone to highillumination. Trips that do not require concentrated movement under anyparticular light for longer than 6 seconds do not result in any of thelights in the zone switching to high illumination, but the zone isilluminated at a relatively dim level to provide some light for thetransient work/movement. All lights in a zone turn off or reduce to thelowest level of illumination, thereby saving energy, when no motion hasbeen detected within the zone for 90 seconds.

As illustrated and explained above with reference to FIG. 7, some of thelighting fixtures in a zone (i.e., the controllers for lighting fixturesin zone) can be set to an ‘general’ mode of operation. FIG. 9illustrates a process 900 for providing an energy saving ‘general’ modeof operation, according to an exemplary embodiment. As is true for theother processes illustrated in the present application, variations(e.g., timing, step ordering, the logic of particular checks and steps,etc.) of process 900 may be made and still fall within the scope of thepresent disclosure. Referring generally to FIG. 9, process 900 isconfigured such that the lighting fixtures are set at a ‘dim’ level ofillumination depending when motion is detected within their assignedzone. If thirty minutes elapses without further motion in the zone, thefixtures turn off (or reduce illumination even further).

As shown in step 902 of process 900, lighting fixture controllers set inan ‘general’ mode of operation cause relay R1 to be ‘on’ by default,providing a ‘dim’ (e.g., not the maximum) level of illumination. TimerT1 (e.g., the time period for which a dim level of illumination shouldbe provided) is initially zero. At step 904 the primary loop of process900 begins or restarts. Periodically (e.g., after a delay cycle, after alogic cycle, etc.) process 900 will check for whether local motion hasbeen detected (step 906). When local motion has been detected,processing electronics of the lighting fixture's controller cause relayR1 to be on such that ‘dim’ illumination is provided from theaccompanying lighting fixture (step 908). A local motion message is alsobroadcasted to other lighting fixtures (i.e., lighting fixturecontrollers having wireless transceivers) in the zone. When local motionis detected, timer T1 is reset to equal thirty minutes. When localmotion is not detected at step 906, process 900 includes checking forwhether a zone motion message was received from another fixture in thezone (step 909). If a zone motion message was received, then relay R1 isenergized (or remains energized), T1 is reset to thirty minutes, and thelocal motion message is rebroadcast (step 908) for reception by yetother fixtures within the zone (which might be out of transmission rangerelative to the devices that originally transmitted the motion message).If neither local motion is detected at step 906 nor a zone motionmessage is received at step 909, timer T1 is decremented by one (step910). If T1 is found to equal zero at step 912, then relay R1 isdeactivated to provide no illumination (step 914). While T1 is not zero(i.e., it has been less than thirty minutes since motion in the zone),decision step 912 causes process 900 to loop back to step 904.

As illustrated and explained above with respect to FIG. 7, some of thelighting fixtures in a zone can be set to a ‘task’ mode of operation.FIG. 10 illustrates a process 1000 for providing an energy saving ‘task’mode of operation, according to an exemplary embodiment. As is true forthe other processes illustrated in the present application, variations(e.g., timing, step ordering, the logic of particular steps and checks,etc.) of process 1000 may be made and still fall within the scope of thepresent disclosure. Referring generally to FIG. 10, process 1000 isconfigured such that the lighting fixtures are set at a relatively dimlevel of illumination in response to motion that is sustained for lessthan five minutes. The lighting fixtures are set at a higher level ofillumination (e.g., ‘high’, ‘occupied’, etc.) when there has been fiveminutes of sustained motion. After five minutes of no motion, thelighting fixtures return to a dim level of illumination. After thirtyminutes of no motion, the lighting fixtures turn off.

As shown in step 1002 of process 1000, lighting fixture controllers setin a ‘task’ mode of operation cause relay R1 to be ‘on’ initially,providing a ‘dim’ (e.g., not the maximum) level of illumination. TimersT1 and T2 (e.g., the time periods for dim lighting and high lighting,respectively) are initially zero. Timers T3 and T4 (used to detectsustained motion) are initially set to five minutes, and two minutes,respectively. The loop begins or repeats at step 1004. When local motionis detected at step 1006, relay R1 is energized (or remains energized),T1 is reset to equal thirty minutes, and a local motion message istransmitted to the other fixtures in the zone (step 1008). If there isno local motion, T4 may be decremented by one (if T4 is not zero) atstep 1022. When local motion is not detected at step 1006, process 1000includes checking for whether a zone motion message was received fromanother fixture in the zone (step 1024). If so, then step 1008 iscalled.

T4 is used as a dwell timer such that up to a two minute break in motioncan elapse before the T3 countdown for sustained motion is reset.Therefore, at step 1010, if T4 is not greater than zero, the timers forT3 and T4 are reset to 5 minutes and 2 minutes, respectively (step1026). If T4 is still greater than zero, process 1000 includes checkingfor sustained task zone motion and if T3 is zero (step 1012). If eitheris true, then sustained motion was detected (either via a message fromanother lighting fixture or via T3 reaching zero, indicating 5 minutesof sustained motion) and relay R2 is energized (or remains energized)(step 1014). Further, T3 is reset to 5 minutes, T4 is reset to 2 minutes(resetting the timers used to detect sustained motion), and a sustainedzone motion message is transmitted to the other fixtures in the zone.Further, if a zone motion message was not received at step 1024, process1000 includes checking for a sustained motion message (step 1028). Ifso, then step 1014 is called.

After process 1000 checks for sustained motion, process 1000 includesdecrementing T1, T2, and T3 by one minute (step 1016). Process 1000 thenchecks if either T1 or T2 is zero (steps 1018, 1020) to determine if thelighting state should change. If T1 is zero, then relay R1 isdeactivated to provide no illumination (step 1030), and if T2 is zero,then relay R2 is deactivated to reduce the lighting from a highillumination level to a dim illumination level (step 1032).

Referring now to FIG. 11, a flow chart of a process 1100 for providing a‘step dimming’ mode of operation, according to an exemplary embodiment.Process 1100 is configured to, upon detection of local motion, providelighting for an area. Upon detection of motion, a high illumination maybe provided by the lighting fixture. After a period of time of nodetected motion, the lighting is reduced from high illumination to dimillumination. After another period of time of no detected motion, thelighting fixture then turns off. As is true for the other processesillustrated in the present application, variations (e.g., timing, stepordering, the logic of particular steps and checks, etc.) of process1100 may be made and still fall within the scope of the presentdisclosure. In the steps of FIG. 11, deactivating a relay may not turnthe lamp entirely off, but may merely step down or step dim aballast/lamp combination.

As shown in step 1102, timers T1 and T2 (representing the time periodsfor dim illumination and high illumination, respectively) are initiallyset to zero. Process 1100 begins or repeats at step 1104. Upon detectionof local motion at step 1106), relay R2 is energized (or remainsenergized), T1 is reset to 30 minutes, T2 is reset to 15 minutes, and alocal motion message is transmitted (step 1108).

Process 1100 further includes decrementing T1 and T2 by one if T1 and T2are not zero (step 1110). Process 1100 further includes checking if T1is now zero (step 1112). If so, then T1 has run out and process 1100includes deactivating relay R1 to provide no illumination (or step-dimthe illumination) (step 1114).

Process 1100 further includes, if R2 is active (step 1116), checking ifT2 is now zero (step 1118). If so, then T2 has run out and process 1100includes deactivating relay R2 to reduce illumination (step 1120).Further, step 1120 includes activating relay R1 since dim lightingshould now be provided instead of high lighting.

Referring now to FIG. 12, a flow chart of a process 1200 for providing aduty cycle mode of operation is shown, according to an exemplaryembodiment. Process 1200 can run in parallel with any of themotion-based control modes described above (e.g., in FIGS. 8-11). Dutycycle mode is intended to protect a lighting fixture ballast/lamps fromcycling too frequently due to the motion based control.

Process 1200 includes determining a setting value, the duty cycle timer,and duty cycle counter (step 1202). The setting value relates to amaximum number of lamp-on transitions (e.g., a transition from localmotion to sustained motion, a transition from ‘standby’ or no motion tolocal motion) that is allowed for the system before a lighting fixtureremain ‘on’ for a longer period of time (preventing premature aging).The setting value may be set automatically or by a user. In process1200, the setting value is set to seven. The duty cycle timer is a setperiod of time (e.g., 24 hours) for which strikes should be counted for.Accordingly, the duty cycle counter is be used to count the number ofmotion-based on transitions during one 24 hour period. Process 1200includes beginning or repeating the loop (step 1204) by determining iflights are detected (step 1206).

The duty cycle timer is checked in step 1208. If the duty cycle timer isnot greater than zero, the duty cycle timer may be started (e.g., startscounting down from 24 hours), the duty cycle counter is reset to zero(step 1212) and the re-strike process (shown in FIG. 13) is called (step1224). If the duty cycle timer is greater than zero, the duty cyclecounter is incremented (step 1210). If the duty cycle counter is lessthan or equal to the setting value determined in step 1202 (step 1214),then the re-strike process is called (step 1224) in order to determineif re-strike protection is in order.

If the duty cycle counter is greater than the setting value, thenprocess 1200 includes activating the motion mode (e.g., turning thelights on) of the lighting fixture (step 1216). The motion mode of thelighting fixture generally represents a desired lighting pattern asdescribed in the disclosure (e.g., the ‘general’ mode of operation ofthe lights, the ‘task’ mode of operation of the lights, the ‘stepdimming’ mode of operation of the lights, etc.).

Process 1200 further includes decrementing the DC timer (step 1218) anddetermining if the DC timer has reached zero (step 1220). If so, themotion mode should be deactivated (step 1222). When the duty cycle timerreaches zero, then the 24 hour period (or another period as determinedin process 1200) has expired and the functionality of the lightingfixture should return to a normal operation (e.g., transitioningaccording to the straight on-off control of one of the motion-basedcontrol modes as shown in FIGS. 8-11 or otherwise).

Referring to FIG. 13, a flow chart of a process 1300 for changing lightfixture states based on re-strike violations is shown, according to anexemplary embodiment. Process 1300 is called by process 1200 and morespecifically step 1224 of FIG. 12.

Process 1300 includes determining if a minimum off-time has expired(step 1304). The minimum off-time relates to motion detection within acertain period of time (e.g., 5 minutes) after lights have been cycledoff. If the minimum off-time has elapsed, the lighting fixture may bereturned to normal control (e.g., the re-strike period is over andregular operation of the lighting fixture resumes), the on-time andre-strike timers are reset to zero for the next time the re-strikeprocess is called, and the re-strike violation counter is reset to zero(step 1320). If the minimum off-time has yet to expire, the motiondetected in process 1200 is determined to be a re-strike violation byprocess 1300.

Process 1300 includes determining if the re-strike violation is thefirst one (step 1306). If so, the lights are activated (step 1308).Further, in step 1308, the re-strike violation timer is started and there-strike violation counter is set to one. The re-strike violation timermay be a set period of time (e.g., 8 hours) for which re-strikeviolations are counted by process 1300. The re-strike violation countercounts the number of violations.

If the re-strike violation was not the first such violation, there-strike violation count is incremented (step 1310). Further, if there-strike violation count is two (step 1330), the lamp on-time may beset to one hour (step 1332), controllably holding the lamp on for atleast one hour regardless of any motion-based inputs. If there are threeor more re-strike violations, the lamp on-time may be set to two hours(step 1334), controllably holding the lamp on for at least two hoursregardless of any motion-based inputs.

Process 1300 further includes checking if the re-strike timer is greaterthan zero (step 1312). If so, the re-strike violation and on-time timersare decremented (step 1316). Otherwise, the re-strike violation timerhas expired and the on-time is re-set to a zero (step 1314) (e.g., theon-time for the lighting fixture relating to a re-strike violation iszero). Process 1300 further includes returning to step 1204 of the dutycycle process of FIG. 12 (step 1318).

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Wheninformation is transferred or provided over a network or anothercommunications connection (either hardwired, wireless, or a combinationof hardwired or wireless) to a machine, the machine properly views theconnection as a machine-readable medium. Thus, any such connection isproperly termed a machine-readable medium. Combinations of the above arealso included within the scope of machine-readable media.Machine-executable instructions include, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing machines to perform a certain function orgroup of functions.

Although the figures may show a specific order of method steps, theorder of the steps may differ from what is depicted. Also two or moresteps may be performed concurrently or with partial concurrence. Suchvariation will depend on the software and hardware systems chosen and ondesigner choice. All such variations are within the scope of thedisclosure. Likewise, software implementations could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps and decision steps.

1. A lighting fixture for energy efficient aisle lighting in a building, comprising: processing electronics configured to cause the lighting fixture to provide increasing levels of illumination in response to state changes associated with sensed motion in the building, wherein the state changes comprise: (a) a transition from a no motion state to a local motion state; and (b) a transition from the local motion state to a sustained motion state.
 2. The lighting fixture of claim 1, wherein the lighting fixture is configured to conduct the state transitions without reliance on a remote supervisory controller and without regular user inputs.
 3. The lighting fixture of claim 1, further comprising: a motion sensor in communication with the processing electronics; wherein the processing electronics transitions from the no motion state to the local motion state in response to estimating motion to be present in an area local to the lighting fixture based on information from the motion sensor.
 4. The lighting fixture of claim 3, wherein the processing electronics cause the lighting fixture to provide less than half of the lighting fixture's capable illumination output while in the local motion state.
 5. The lighting fixture of claim 3, wherein the processing electronics cause the lighting fixture to provide more than half of the lighting fixture's capable illumination output while in the sustained motion state.
 6. The lighting fixture of claim 1, wherein the state changes further comprise: (c) a transition from the sustained motion state to the no motion state; and (d) a transition from the local motion state to the no motion state.
 7. The lighting fixture of claim 1, wherein the state changes further comprise: (c) a transition from the sustained motion state to the local motion state; and (d) a transition from the local motion state to the no motion state.
 8. The lighting fixture of claim 1, further comprising: an RF receiver; wherein the state changes further comprise: (c) a transition from the local motion state to a communicated sustained motion state; wherein the processing electronics are configured to transition from the local motion state to the communicated sustained motion state in response to a reception at the RF receiver indicating sustained motion in a zone associated with the lighting fixture; wherein the processing electronics cause the lighting fixture to provide more than half of the lighting fixture's capable illumination output while in the communicated sustained motion state.
 9. A system for energy efficient lighting of an aisle in a building, comprising: a plurality of lighting fixtures, wherein each of the plurality of lighting fixtures comprises a motion sensor, a transceiver, and processing electronics, and wherein the processing electronics for each lighting fixture are configured to cause the respective lighting fixture to provide increasing levels of illumination in response to state changed associated with motion sensed by the motion sensor, wherein the state changes comprise (a) a transition from a no motion state to a local motion state; and (b) a transition from the local motion state to a sustained motion state.
 10. The system of claim 9, wherein the processing electronics are configured to initiate the transition from the local motion state to the sustained motion state when motion is detected with for longer than a predetermined period of time.
 11. The system of claim 10, wherein the processing electronics are configured to cause the transceiver to transmit a message indicating the transition to the sustained motion state.
 12. The system of claim 11, wherein the processing electronics are configured to cause the transition to the sustained motion state in response to receiving a message at the transceiver indicating a transition to the sustained motion state by a nearby lighting fixture.
 13. The system of claim 12, wherein each lighting fixture is configured to cause the lighting fixture to provide less than half of the lighting fixture's capable illumination output while in the local motion state.
 14. The system of claim 13, wherein each lighting fixture is configured to cause the lighting fixture to provide more than half of the lighting fixture's capable illumination output while in the sustained motion state.
 15. The system of claim 14, wherein the state changes further comprise: (c) a transition from the sustained motion state to the no motion state; and (d) a transition from the local motion state to the no motion state.
 16. A method for providing energy efficient lighting of an aisle in a building, comprising: using a motion sensor and processing electronics coupled to a first lighting fixture to distinguishing between transient motion and sustained motion, wherein distinguishing between the transient motion and the sustained motion comprises determining that motion has been detected in a space for at least a predetermined period of time; at the first lighting fixture, transitioning from a transient motion state to a sustained motion state in response to a determination of sustained motion; and at the first lighting fixture, transitioning from a no motion state to a local motion state in response to a determination of local motion.
 17. The method of claim 16, further comprising: transmitting a notification to a nearby lighting fixture that indicates sustained motion has been detected; responding to receiving the notification, at the nearby lighting fixture, by determining whether to transition into a different lighting state.
 18. The method of claim 17, wherein the different lighting state is a sustained motion state and wherein the nearby lighting fixture transitions into the sustained motion state when processing electronics of the nearby lighting fixture determines that the received notification was received within a predetermined period of time from a detection of local motion wherein the first lighting fixture and the nearby lighting fixture are configured to transition from the sustained motion state to a local motion state after a second predetermined period of time.
 19. The method of claim 16, further comprising: at the first lighting fixture, counting a ballast re-strike violation when a motion-based transition causes a transition into a sustained motion state within a period of time since the fixture transitioned out of the sustained motion state; controlling the first lighting fixture to remain in the sustained motion state for a longer period of time than motion-based control would otherwise provide in response to the count of re-strike violations exceeding a pre-set amount.
 20. The method of claim 16, further comprising: tracking the number of times the first lighting fixture transitions from the local motion state to the sustained motion state; controlling the first lighting fixture to remain in the sustained motion state for a longer period of time than the motion-based control would otherwise provide in response to the number of times the first lighting fixture transitioned from the local motion state to the sustained motion state. 